Hypothesis testing lead time
hiroki_daichi: Principles such as Agile are often explained in relation to "speed and agility" because of the meaning of the word, which makes them difficult to understand. The key principle in software development is "Fail-Fast", and the principle of static typing, automated testing, chaos engineering, scrum development, and product management is "premature failure". hiroki_daichi: if you are associated with speed, you may lean toward "make it in a hurry" or "make it with no time to spare". To fail early, it becomes hypothesis-testing lead-time thinking. Thinking to identify what is the most volatile risk is required. nishio: "It is important to shorten the lead time for hypothesis testing, and this requires thinking to identify what is the most volatile risk", I completely I agree with you, but I'm trying to think of a better way to explain this to middle and high school students, because I don't think they will get it. nishio: In the proposal "If you make B from A and C from B, the customer will be happy", if it is "unclear whether the method of making B from A will work" and you say "I made a prototype of making C from B. If the method of making C from B is not clear, then the work will be meaningless if the process does not go as planned between A and B. The feeling of "I'm not sure how to make B from A. https://gyazo.com/b57e1a829450f689f8863544383e4945
nishio: in other words, it is the most uncertain arrows that should be prototyped and verified. We need to identify which is the weakest arrow in the arrow connection and make a prototype to check if it is not broken. If it's broken, it's in our best interest to notice it as soon as possible. This is what I mean by "it pays to fail fast." nishio: Maybe, but you're thinking of asking a mentor to teach you after you've been adopted because you're worried about your AB arrows, but even if you're asking for advice, it's easier to give feedback if you say "I didn't do anything, tell me about it. I'm not doing anything, tell me what you did", it is easier to give feedback if you say "I thought it would be good to do this, but the result was different from what I expected. hiroki_daichi: note.com/hirokidaichi/n... I often use episodes of summer homework. I often use episodes of summer vacation homework. Please let me know if you have any good phrases. nishio: "Summer homework, if you do it from what you're good at, you're left with the things you're not good at, and that's a bit depressing. The analogy of "it's better to do it from what you are not good at first" is good for the atmosphere, but there is no dependency between the tasks. If you put off the free research you're not good at and don't finish it during summer vacation, it doesn't invalidate the kanji drills you're good at that you did first twitter.com/hiroki_daichi/... nishio: when the arrows are in series, like "make B from A and C from B", if one arrow is broken, the whole thing is ruined. So you need to check the weakest arrow first. ---
This page is auto-translated from /nishio/仮説検証のリードタイム using DeepL. If you looks something interesting but the auto-translated English is not good enough to understand it, feel free to let me know at @nishio_en. I'm very happy to spread my thought to non-Japanese readers.